Storage Apparatus and Method of Managing Data Storage Area

ABSTRACT

Disclosed is a storage apparatus that extends endurance and reduces bit cost. A storage apparatus includes a controller and a semiconductor storage media that has a plurality of storage devices. The plurality of storage devices include a first storage device and a second storage device having an upper limit of an erase count of data smaller than that of the first storage device. Area conversion information includes correspondence of a first address to be specified as a data storage destination and a second address of an area in which data is to be stored. A rewrite frequency of stored data is recorded for each area. The controller selects an area corresponding to the first address, determines whether or not the rewrite frequency of the selected area is equal to or larger than a first threshold value, when the rewrite frequency is equal to or larger than the threshold value, selects an area to be provided by the first storage device, and when the rewrite frequency is smaller than the threshold value, selects an area to be provided by the second storage device and maps the address of the selected area to the first address.

CROSS REFERENCES TO RELATED APPLICATIONS

This application relates to and claims priority from Japanese PatentApplication No. 2008-279661, filed on Oct. 30, 2008, the entiredisclosure of which is incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a storage apparatus having asemiconductor storage media, and in particular, to a technology formanaging a data storage area.

2. Description of the Related Art

In recent years, a nonvolatile semiconductor memory, such as a flashmemory, which supports high-speed access, is attracting attention. Aflash memory which has come into wide use is called a NAND flash memory,and is divided into MLC (Multiple Level Cell) and SLC (Single LevelCell) according to the characteristic of the storage device. The MLC hasa storage capacity of two or more bits per memory cell, and has featuresof low bit cost, low performance, and short endurance. The SLC has astorage capacity of one bit per memory cell, and has features of highbit cost, high performance, and long endurance.

The flash memory includes a plurality of flash memory chips. Each of theflash memory chips has a plurality of memory blocks (hereinafter,referred to as “block”) for storing data. The flash memory has a featurethat data is erased in a block unit. In the flash memory, a bit can onlybe changed in one direction (1→0), and in order to change a bit in theother direction, it is necessary to erase a block once and to change allthe blocks to 1. However, an erase count of a block in the flash memoryhas an upper limit (100000 in the SLC and 10000 in the MLC). In a block(hereinafter, referred to as “worn-out block”) in which the erase countreaches the upper limit, an error may occur during the read and writeoperations.

For this reason, when a flash memory as a substitute for a hard disk iscoupled to a computer, only some of blocks may reach the upper limit ofthe erase count due to a bias of a write frequency for each block, andmay be disabled. In order to solve this problem, JP-A-2007-305210discloses a technology that stores data, which is predicted to have ahigh rewrite frequency, in an SLC area in advance, and stores data,which is predicted to have a low rewrite frequency, in an MLC area inadvance.

The SSD (Solid State Drive) as a storage apparatus using a flash memoryincludes an SSD having a flash memory of one type of SLC or MLC and anSSD having flash memories of SLC and MLC. In an SSD having SLC and MLC,like the technology disclosed in JP-A-2007-305210, the storagedestination of data is defined depending on the contents or thecharacteristics of data to be stored. The SSD has substitute blocks as asubstitute area in advance therein. When all the substitute blocks areused up, the SSD becomes unwritable, and the SSD is worn out.

When the SSD is mounted as a storage media of a storage system, thefollowing three modes may be considered depending on the type of theflash memory forming the SSD: one of an SSD having an SLC and an SSDhaving an MLC is used; an SSD having an SLC and an SSD having an MLC areused together; and an SSD having an SLC and an MLC is used. When such anSSD is mounted on a storage system, a different SSD is allocated as asubstitute for an SSD (hereinafter, referred to as “worn-out SSD”) whichbecomes unwritable because all the substitute blocks are used up.

SUMMARY OF THE INVENTION

According to the technology disclosed in JP-A-2007-305210, a datastorage area is sorted into the SLC or the MLC depending on a rewritefrequency of data, thereby preventing data from being biasedly writtenin a specific memory block.

According to the technology disclosed in JP-A-2007-305210, however, datato be allocated to the SLC and the MLC is fixed in advance, and the typeof the substitute block is fixed. For this reason, when the rewritefrequency of data stored in the MLC becomes high, the MLC is expected tobe rapidly worn out. Accordingly, the substitute blocks of the MLC arelikely to be drained, and the endurance of the SSD decreases. Thedecrease in the endurance of the SSD causes an increase in substitutionfrequency of the SSD, and as a result, bit cost increases. When therewrite frequency of data stored in the SLC becomes low, even datahaving a low rewrite frequency is continuously stored in the SLC of highbit cost, and as a result, bit cost increases.

If an SSD is mounted on a known storage system, when a different SSD asa substitute for a worn-out SSD is allocated, the type of the SSD isselected without taking an access status to the worn-out SSD. Forexample, when the rewrite frequency of data stored in the SLC decreases,although bit cost can be decreased when data is stored in the MLC, datais continuously stored in the SLC. For this reason, bit cost increases.When the rewrite frequency of data stored in the MLC increases, althoughthe endurance can be extended when data is stored in the SLC, data iscontinuously stored in the MLC. For this reason, the endurance of theMLC is shortened. As a result, the endurance of the entire SSD isshortened.

When an SSD having an SLC and an MLC together is mounted on a storagesystem, when the substitute blocks of one of the SLC and the MLC areused up and the SSD is worn out, the SSD should be substituted with adifferent SSD, and a sufficient number of blocks of the other one of theSLC and the MLC cannot be used. For example, when no MLC area remains inthe SSD, the SSD having a sufficient number of SLC areas has to besubstituted whole, and the SLC areas cannot be used. As described above,when an SSD is substituted in a state where a sufficient number ofblocks remain in the SSD, it may be impossible to optimize bit cost.

According to an embodiment of the invention, a storage apparatusincludes a semiconductor storage media that has a plurality of storagedevices, and a controller that is coupled to the semiconductor storagemedia. Each of the storage devices has an upper limit of an erase countof data stored therein. The plurality of storage devices include a firststorage device and a second storage device having an upper limit smallerthan that of the first storage device. The controller includes aninterface, a processor that is coupled to the interface, and a memorythat is coupled to the processor. The memory stores storage mediamanagement information that is used to manage the semiconductor storagemedia. The storage media management information includes area conversioninformation including the correspondence of a first address to bespecified as a storage destination of data and a second address of anarea where data is stored, and a rewrite frequency of stored data isrecorded for each area. The controller selects an area corresponding tothe first address, acquires the rewrite frequency of the selected areafrom the storage media management information, determines whether or notthe acquired rewrite frequency is equal to or larger than a firstthreshold value, when the acquired rewrite frequency is equal to orlarger than the first threshold value, selects a first area to beprovided by the first storage device, when the acquired rewritefrequency is smaller than the first threshold value, selects a secondarea to be provided by the second storage device, and sets a secondaddress of the selected first area or second area to the second addresscorresponding to the first address, to thereby update the areaconversion information.

According to the embodiment of the invention, in a storage apparatushaving a plurality of types of storage devices (flash memories),endurance of the storage apparatus can be extended and bit cost can bereduced.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing an example of an SSD as a storageapparatus using a flash memory according to a first embodiment of theinvention;

FIG. 2 is a diagram showing an example of block management informationaccording to the first embodiment of the invention;

FIG. 3 is a flowchart showing an example of a writing processingprocedure according to the first embodiment of the invention;

FIG. 4 is a flowchart showing an example of a worn-out blocksubstitution processing procedure according to the first embodiment ofthe invention;

FIG. 5 is a flowchart showing an example of a block substitutionprocessing procedure according to the first embodiment of the invention;

FIG. 6 is a diagram illustrating a pattern of selection of a substituteblock according to the first embodiment of the invention;

FIG. 7 is a block diagram showing an example of the configuration of acomputer system according to a second embodiment of the invention;

FIG. 8 is a diagram showing an example of block management informationaccording to the second embodiment of the invention;

FIG. 9 is a flowchart showing an example of a worn-out blocksubstitution processing procedure according to the second embodiment ofthe invention;

FIG. 10 is a diagram showing an example of a RAID group having flashmemory packages in a storage system according to the second embodimentof the invention;

FIG. 11 is a block diagram showing an example of the configuration of acomputer system according to a third embodiment of the invention;

FIG. 12 is a diagram showing an example of SSD management informationaccording to the third embodiment of the invention;

FIG. 13 is a flowchart showing an example of a substitution processingprocedure of a worn-out SSD according to the third embodiment of theinvention;

FIG. 14 is a flowchart showing an example of an SSD substitutionprocessing procedure according to the third embodiment of the invention;and

FIG. 15 is a flowchart showing an example of an erase block substitutionprocessing procedure according to a fourth embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

Embodiments of the invention will now be described with reference to thedrawings.

First Embodiment

A first embodiment will now be described with reference to FIGS. 1 to 6.

FIG. 1 is a block diagram showing an example of an SSD 100 as a storageapparatus using a flash memory according to the first embodiment of theinvention.

The SSD 100 includes an SSD controller 101, an SLC flash memory module102, and an MLC flash memory module 103.

The SSD controller 101 controls the entire SSD 100. The SSD controller101 has a processor 105, an interface 106, and block managementinformation 200. The processor 105 controls data input/output. Theinterface 106 receives a data input/output request. The block managementinformation 200 stores information for managing blocks 104.

The SLC flash memory module 102 and the MLC flash memory module 103 arecoupled to the SSD controller 101. The flash memory module is a memorymodule in which a plurality of flash memory chips are mounted on aprinted board. The flash memory module has a plurality of blocks 104that store data therein.

FIG. 2 is a diagram showing an example of the block managementinformation 200 according to the first embodiment of the invention.

The block management information 200 includes a block conversion table201, an SLC substitute block list 205, an MLC substitute block list 206,a block information table 207, a substitute block counter 211, a badblock counter 213, and a threshold value table 230.

The block conversion table 201 is a mapping table of logical blockaddress 202 and physical block address 203. The logical block address202 indicates the location of a block in a logical address space. Thephysical block address 203 indicates the location of a block of aphysical flash memory chip allocated with the logical block address 202.

The SLC substitute block list 205 is a list of physical block addresses203 of SLC blocks, to which no storage area is allocated but a storagearea is allocatable, from among blocks in the SSD.

The MLC substitute block list 206 is a list of physical block addresses203 of MLC blocks, to which no storage area is allocated but a storagearea is allocatable, from among blocks in the SSD.

The block information table 207 is a table that manages information,such as a rewrite frequency, an erase count, and whether or not a blockis a worn-out block, for each allocated block. The block informationtable 207 includes physical block address 203, SLC/MLC ID 204, rewritefrequency 208, erase count counter 209, and endurance flag 210.

The SLC/MLC ID 204 is an identifier indicating whether the type of amemory module allocated with a block corresponding to the physical blockaddress 203 is SLC or MLC.

The rewrite frequency 208 is an indicator which is used to determinewhether the type of a substitute block to be allocated as a substitutewhen a block becomes a worn-out block is SLC or MLC. For example, acycle of rewriting during a predetermined period may be used. Inaddition, a time at which a corresponding block is last substituted maybe stored, and a time elapsed from a last substitution processing may beused as the rewrite frequency.

The erase count counter 209 is the number of erase count for each block,and is incremented each time a block is erased. The erase count counter209 is an indicator which is used to determine whether or not a block isworn out.

The endurance flag 210 is information indicating whether or not a blockis a worn-out block. For example, the endurance flag is set to “0” in aninitial state, and when the erase count exceeds a reference value, it isset to “1”. A block with the endurance flag 210 set to “1” becomes aworn-out block.

The substitute block counter 211 indicates the number of remainingsubstitute blocks. The substitute block counter 211 includes SLC/MLC ID204 and the number 212 of substitute blocks. The substitute blockcounter 211 stores the number of substitute blocks for SLC or MLC.

The bad block counter 213 stores the number of blocks which are unusabledue to endurance or physical failure. The bad block counter 213 includesSLC/MLC ID 204 and the number 212 of substitute blocks. The bad blockcounter 213 stores the number of bad blocks for each of the SLC and theMLC. Before the system operates, the number of initial bad blocks in aflash memory is acquired and set as an initial value.

The threshold value table 230 stores a threshold value which is used todetermine whether or not to substitute a block and a threshold valuewhich is used to determine the type of a block as a substitute.

A substitute block selection procedure according to the first embodimentof the invention will be described. In the first embodiment, when datais written, it is determined on the basis of an erase count of datawhether or not to substitute a target block in which data is to bewritten. In addition, it is determined the type of a block as asubstitute on the basis of the write frequency of the target block inwhich data is to be written.

According to the first embodiment of the invention, a block substitutionprocessing is executed when it is determined that a block has to beerased, but the invention is not limited thereto. The block substitutionprocessing may be executed in various ways. For example, the blocksubstitution processing may be executed periodically.

First, a writing processing procedure with respect to a flash memorywill be described.

FIG. 3 is a flowchart showing an example of a writing processingprocedure according to the first embodiment of the invention.

If a write request (write command) is received (Step 320), the processor105 of the SSD controller 101 refers to the block conversion table 201,acquires the physical block address 203 corresponding to the logicalblock address 202 of a write destination in the write command, andspecifies a write data storage destination block (Step 321).

The processor 105 of the SSD controller 101 refers to the endurance flag210 in the block information table 207 corresponding to the write datastorage destination block, and specifies whether or not the value of theendurance flag 210 is “0” (OFF) (Step 322).

When the endurance flag 210 is not “0” (OFF), that is, when theendurance flag 210 is “1” (ON) (“No” in Step 322), the write datastorage destination block is a worn-out block. Thus, the processor 105of the SSD controller 101 can recognize that the block substitutionprocessing is being executed. Therefore, the processor 105 waits foruntil the block substitution processing ends, and the value of physicalblock address 203 in the block conversion table 201 is changed (Step323). Next, the process returns to Step 321.

When the endurance flag 210 is “0” (OFF) (“Yes” in Step 322), the writedata storage destination block is not a worn-out block, and thus theprocessor 105 of the SSD controller 101 can store data in thecorresponding block. Next, the processor 105 of the SSD controller 101determines whether or not the write data storage destination block hasto be erased once (Step 324). When the write data storage destinationblock does not have to be erased once (“No” in Step 324), that is, whendata can be stored in the write data storage destination block as it is,data is written in the write data storage destination block (Step 327).Thus, this processing ends.

When the write data storage destination block has to be erased once(“Yes” in Step 324), the processor 105 of the SSD controller 101executes a worn-out block substitution processing with respect to thewrite data storage destination block (Step 3000). The details of theworn-out block substitution processing will be described below withreference to FIG. 4.

If the worn-out block substitution processing is completed, processor105 of the SSD controller 101 writes data in the write data storagedestination block (Step 327). Thus, this processing ends.

FIG. 4 is a flowchart showing an example of a worn-out blocksubstitution processing according to the first embodiment of theinvention.

When a block is erased, the processor 105 of the SSD controller 101refers to the substitute block counter 211, and determines whether ornot the number 212 of substitute blocks is larger than a prescribedthreshold value (Step 300). The threshold value is preferably set suchthat it is possible to determine that the substitute blocks of the SLCand the substitute blocks of the MLC are equal to or larger than apredetermined number of blocks. The threshold value needs to be set inthe threshold value table 230 in advance, but it may be reset dependingon the status of the SSD 100.

When the number 212 of substitute blocks is smaller than the prescribedthreshold value (“No” in Step 300), since the SSD 100 is close to anexpected endurance, the processor 105 of the SSD controller 101 notifiesan initiator coupled to the SSD 100 or a computer having the initiatorthat a small number of substitute blocks remains (Step 307).

When the number 212 of substitute blocks is equal to or larger than theprescribed threshold value (“Yes” in Step 300), or when Step 307 ends,the processor 105 of the SSD controller 101 determines whether or not anerased block is a worn-out block.

The processor 105 of the SSD controller 101 first refers to the erasecount counter 209 corresponding to the erased block in the blockinformation table 207 (Step 301). Next, it is determined whether or notthe erase count counter 209 of the erased block is equal to or largerthan a prescribed threshold value, that is, the erased block is aworn-out block (Step 302).

When the erase count counter 209 of the erased block is smaller than theprescribed threshold value, that is, when the erased block is not aworn-out block (“No” in Step 302), the processor 105 of the SSDcontroller 101 erases a storage destination block in which data is to bewritten (Step 325). Next, the value of the erase count counter 209 ofthe block information table 207 is incremented by 1 (Step 326), and thenthis processing ends.

When the value of the erase count counter 209 of the erased block isequal to or larger than the threshold value (“Yes” in Step 302), theprocessor 105 of the SSD controller 101 sets the endurance flag 210 ofthe block information table 207 to “1” (ON) (Step 303). Next, a blocksubstitution processing for allocating a block as a substitute for aworn-out block is executed (Step 304). The details of the blocksubstitution processing will be described below with reference to FIG.5.

If the block substitution processing (Step 304) is completed, theprocessor 105 of the SSD controller 101 deletes the physical blockaddress 203 of the substituted block from the SLC substitute block list205 or the MLC substitute block list 206, and decrements the quantity212 of the substitute block counter 211 by 1 (Step 305).

The processor 105 of the SSD controller 101 increments the quantity 212of the bad block counter 213 corresponding to the SLC/MLC ID 204 withrespect to the worn-out block by 1 (Step 306).

FIG. 5 is a flowchart showing an example of a block substitutionprocessing procedure according to the first embodiment of the invention.

The processor 105 of the SSD controller 101 refers to the rewritefrequency 208 in the block information table 207 with respect to theworn-out block (Step 309), and determines whether or not the rewritefrequency 208 is equal to or larger than a prescribed threshold value(Step 310).

In Step 310, although the rewrite frequency 208 is used as a selectioncriterion of the type of the substitute block, for example, the type ofthe substitute block may be selected on the basis of a ratio of thenumber of substitute blocks of the SLC and the number of substituteblocks of the MLC to be acquired from the substitute block counter 211,or on the basis of a ratio of the number of bad blocks of the SLC andthe number of bad blocks of the MLC to be acquired from the bad blockcounter 213.

In the first embodiment of the invention, when the rewrite frequency 208is equal to or larger than the threshold value, it can be determinedthat data having a high rewrite frequency is stored in the worn-outblock. Therefore, allocation of an SLC having a high upper limit of anerase ensures extension of endurance. When the rewrite frequency 208 issmaller than the threshold value, it can be determined that data havinga low rewrite frequency is stored in the worn-out block. Therefore,allocation of an MLC having a low upper limit of an erase count but lowbit cost ensures reduction in bit cost.

When data having a high rewrite frequency is stored in the worn-outblock (“Yes” in Step 310), the processor 105 of the SSD controller 101selects an SLC as a substitute block. Next, data stored in the worn-outblock is copied to the selected substitute block of the SLC (Step 311).If data is copied from the worn-out block to the substitute block, thephysical block address 203 in the block conversion table 201 withrespect to the worn-out block is changed to the physical block address203 of the substitute block (Step 312).

Similarly, when data having a low rewrite frequency is stored in theworn-out block (“No” in Step 310), the processor 105 of the SSDcontroller 101 selects an MLC as a substitute block. Next, data storedin the worn-out block is copied to the selected substitute block of theMLC (Step 313). If data is copied from the worn-out block to thesubstitute block, the physical block address 203 in the block conversiontable 201 with respect to the worn-out block is changed to the physicalblock address 203 of the substitute block (Step 314).

In the flowchart of FIG. 5, a case in which the substitute block of theSLC and the substitute block of the MLC are usable has been described,but when only one substitute block is usable, a usable substitute blockmay be forcibly selected.

Although the substitution processing procedure of the worn-out block tobe executed when a block is erased has been described, when an erasefrequency is high, the substitution processing of the worn-out block maybe further executed, and accordingly processing overhead may increase.In such a case, if the substitution processing of the worn-out block isexecuted periodically, the number of processing times can be reduced,and thus the processing overhead can be reduced. When the substitutionprocessing of the worn-out block is executed periodically, the procedureshown in FIG. 5 may be executed for all the blocks.

According to the above-described processing procedure, the storagedestination block is selected on the basis of the rewrite frequency ofdata, and thus the endurance of the SSD 100 can be extended.

Finally, a pattern of selection of a substitute block will be described.

FIG. 6 is a diagram illustrating a pattern of selection of a substituteblock according to the first embodiment of the invention.

As the pattern of selection of a substitute block, for example, as shownin FIG. 6, a block 104 in the same flash memory module may be selectedas a substitute block, or a block 104 in a different flash memory modulemay be selected as a substitute block.

Although a method of selecting a substitute block is not specifiedherein, a substitute block may be selected depending on priority. Forexample, a substitute block in the same flash memory module may beselected preferentially, or a substitute block in a different flashmemory module may be selected preferentially.

According to the first embodiment of the invention, the type of thesubstitute block is selected on the basis of the rewrite frequency, andthus an increase in the endurance of the entire storage apparatus andthe reduction in bit cost can be achieved. Specifically, if an SLC isused as a substitute block for a block having a high rewrite frequency,the endurance of the storage apparatus can be extended. If an MLC isused as a substitute block for a block having a low rewrite frequency,bit cost can be reduced.

Second Embodiment

According to the first embodiment of the invention, the invention isapplied to the SSD including the SSD controller, but according to asecond embodiment, the invention is applied to a storage system havingmounted thereon a plurality of flash memory modules. In the secondembodiment, instead of the SSD controller, a storage controller controlsdata input/output with respect to the flash memory modules.

Hereinafter, the second embodiment will be described with reference toFIGS. 7 to 10. In the second embodiment, the same contents as the firstembodiment will be appropriately omitted.

FIG. 7 is a block diagram showing an example of the configuration of acomputer system according to the second embodiment of the invention.

The computer system according to the second embodiment of the inventionincludes a storage system 400, a host computer 401, and a managementserver 402.

The storage system 400 stores data to be read and written by the hostcomputer 401. The storage system 400 is coupled to the host computer 401and the management server 402. The host computer 401 sends a dataread/write request to the storage system 400. The management server 402manages the storage system 400.

The storage system 400 includes a storage controller 403 and a pluralityof flash memory packages. The storage controller 403 controls the entirestorage system 400. The plurality of flash memory packages include SLCpackages 408 and MLC packages 409. The storage controller 403 is coupledto the SLC packages 408 and the MLC packages 409.

The storage controller 403 includes a port 404, a processor 405, a cachememory 406, and a main memory 407. The port 404, the processor 405, thecache memory 406, and the main memory 407 are coupled to each otherthrough an internal network 430.

The port 404 is coupled to the host computer 401 and the managementserver 402. At least one port 404 is provided in the storage controller403. For example, one port may be coupled to the management server 402,and other ports may be coupled to the host computer 401.

The processor 405 processes a data input/output request with respect tothe storage system 400 on the basis of a control program and controlinformation stored in the main memory 407.

The cache memory 406 temporarily stores data for the sake of high-speedinput/output of data stored in the flash memory packages.

The main memory 407 stores block management information 250, which ismanagement information of blocks in the flash memory packages, and alsostores a control program and control information for controlling theentire storage system 400.

Each of the SLC packages 408 includes, for example, a plurality ofmemory modules, a connector, a slot, and a control unit. Each memorymodule is a storage media in which data is stored, for example, an SLCflash memory module 102 in which a plurality of SLC flash memory chipsare mounted on a printed board. The SLC flash memory module 102 is thesame as the SLC flash memory module 102 in the SSD according to thefirst embodiment.

The connector is an interface for connection to the storage controller403. The slot is an interface for connection of the memory module to theSLC package 408. The control unit controls access to the flash memorychips.

The MLC packages 409 are the same as the SLC packages 408, except thatthe type of a flash memory to be mounted on the memory module is an MLC.The memory module is the same as the MLC flash memory module 103 in theSSD according to the first embodiment.

The storage system 400 includes at least one supplemental package slot410 that is used to add the SLC package 408 and the MLC package 409 orone of them.

When the SLC package 408 or the MLC package 409 is added to the storagesystem 400, the block management information 250 stored in the mainmemory 407 is updated by the processor 405. The details of the updatewill be described with reference to FIG. 8.

FIG. 8 is a diagram showing an example of the block managementinformation 250 according to the second embodiment of the invention.

The block management information 250 includes a block conversion table201, an SLC substitute block list 205, an MLC substitute block list 206,a block information table 207, a substitute block counter 211, a badblock counter 213, a mapping table 214, and a threshold value table 230.

The block conversion table 201, the SLC substitute block list 205, theMLC substitute block list 206, the block information table 207, thesubstitute block counter 211, the bad block counter 213, and thethreshold value table 230 have the same configuration as those in thefirst embodiment.

The mapping table 214 includes WWN (World Wide Name) 215, Port# 216, LUN217, and LDEV# 218.

The WWN 215 is a number for identifying the ports 404 which is aninterface coupled to the host computer 401. The WWN 215 is an identifierto be uniquely identified by the host computer 401. The Port# 216 is anumber for identifying the port 404 in the storage system 400.

The LUN 217 is a number which is used by the host computer 401 toidentify a logical volume. The LDEV# 218 is a number for identifying alogical volume in the storage system 400.

As described above, when the SLC package 408 or the MLC package 409 isadded to the storage system 400, the block management information 250 isupdated. Specifically, when the SLC package 408 is added to the storagesystem 400, the physical block address 203 of a block 104 of the addedSLC package 408 is added to the SLC substitute block list 205. Thequantity 212 of the substitute block counter 211 is added by the numberof added blocks.

Similarly, when the MLC package 409 is added to the storage system 400,the physical block address 203 of a block 104 of the added MLC package409 is added to the MLC substitute block list 206. The quantity 212 ofthe substitute block counter 211 is added by the number of added blocks.

FIG. 9 is a flowchart showing an example of a worn-out blocksubstitution processing procedure according to the second embodiment ofthe invention.

A difference from the worn-out block substitution processing accordingto the first embodiment of the invention shown in FIG. 3 is that,instead of the processor 105 of the SSD in the first embodiment, theprocessor 405 of the storage controller 403 executes the processing. Inthe second embodiment, a message to be displayed when a substitute blockis smaller than a threshold value is also different from that in thefirst embodiment. Others are the same as those in the first embodiment.

Similarly to the first embodiment, if a block is erased, the processor405 of the storage controller 403 refers to the substitute block counter211, and determines whether or not the quantity 212 of the substituteblocks is equal to or larger than a prescribed threshold value (Step300). The threshold value is set in the same manner as the firstembodiment.

When the quantity 212 of the substitute blocks is smaller than theprescribed threshold value (“No” in Step 300), since a substitute blockcannot be allocated in a short time, the processor 405 of the storagecontroller 403 displays a message to urge addition of an SLC package 408or an MLC package 409. In this case, the number of substitute blocks iscompared with a threshold value for each type of memory module.

The processor 405 of the storage controller 403 first determines whetheror not the number of substitute SLC blocks is smaller than a thresholdvalue (Step 331). When the number of substitute SLC blocks is smallerthan the threshold value (“Yes” in Step 331), a message to urge additionof an SLC package 408 is displayed (Step 332).

Next, the processor 405 of the storage controller 403 determines whetheror not the number of substitute MLC blocks is smaller than a thresholdvalue (Step 333). When the number of substitute MLC blocks is smallerthan the threshold value (“Yes” in Step 333), a message to urge additionof an MLC package 409 is displayed (Step 334).

The threshold values used in Steps 331 and 333 may have the same valueor may be set depending on the type of the memory module. The messagesto be displayed in Steps 332 and 334 are output to, for example, themanagement server 402.

When the number of substitute blocks is equal to or larger than thethreshold value, or after the message is displayed, in regard to Step301 and later, the same processing as the first embodiment shown in FIG.3 is executed.

According to the second embodiment of the invention, an RAID can beconstructed in order to increase reliability as a storage system.

FIG. 10 is a diagram showing an example of a RAID group having flashmemory packages in the storage system 400 according to the secondembodiment of the invention.

FIG. 10 shows an example where a RAID4 having three data (D) and oneparity (P) is constructed. In this case, as the type of the flashmemory, one of an SLC and an MLC may be used, or an SLC and an MLC maybe used together. Different RAID configuration, for example, RAID5, maybe constructed.

According to the configuration shown in FIG. 10, MLC packages 409A to409C are used as the flash memory packages, in which data is stored, andan SLC package 408A is used as a flash memory package, in which parityis stored. The parity is updated each time data stored in each flashmemory package is updated, and thus an SLC having a long endurance isused.

When a RAID is formed by a plurality of SLC packages 408 or MLC packages409, in order to secure redundancy, the substitute blocks are preferablyallocated such that two or more of data or parities in the same RAIDconfiguration are not included in one SLC package 408 or one MLC package409 forming the RAID.

If the same data is stored in a block on a different flash memorypackage, RAID1 (mirroring) maybe constructed. In this case, the RAID1may be formed by different SLC packages 408, different MLC packages 409,or an SLC package 408 and an MLC package 409.

In the flash memory, in addition to the endurance based on the erasecount, an error may occur due to a physical failure, and data stored ina block may not be read. When a substitution processing of a block inwhich an error occurs is executed, data cannot be read from the blockout of order. For this reason, in the above-described block substitutionprocessing, the substitution processing may not be normally executed.

According to the second embodiment of the invention, data becomesredundant, and a RAID group can be constructed. For this reason, eventhough data stored in a block forming the RAID group is not read due toa physical failure, correction copy can be performed to restore datastored in the block out of order on the basis of data and parity formingthe RAID group.

In the substitution processing by correction copy, in Steps 311 and 313,data stored in a failed block is restored by correction copy, and isstored in a substitute block. During the substitution processing bycorrection copy, in selecting the type of the substitute block, it isnecessary to grasp a parameter, such as a rewrite frequency, before theblock is out of order. Therefore, as the threshold value for determiningthe type of the substitute block, a rewrite frequency during apredetermined period is preferably used.

According to the second embodiment of the invention, in addition to thesame advantages as the first embodiment, since data becomes redundantand is stored, data can be restored from an error due to a physicalfailure.

Third Embodiment

According to the second embodiment of the invention, the invention isapplied to the storage system having flash memory packages, butaccording to a third embodiment, the invention is applied to a storagesystem having mounted thereon SSDs, not flash memory package. In thethird embodiment, a storage controller controls SSDs.

Hereinafter, the third embodiment will be described with reference toFIGS. 11 to 14. In the third embodiment, the same contents as the firstembodiment or the second embodiment will be appropriately omitted.

FIG. 11 is a block diagram showing an example of the configuration of acomputer system according to the third embodiment of the invention.

Similarly to the second embodiment, the computer system according to thethird embodiment of the invention includes a storage system 400, a hostcomputer 401, and a management server 402. The third embodiment has thestorage system 400 different from the second embodiment.

The storage system 400 includes a storage controller 403 and a pluralityof SSDs. The storage controller 403 controls the entire storage system400. The plurality of SSDs include SSDs having an SLC (hereinafter,referred to as “SSD(S)”) 107 and SSDs having an MLC (hereinafter,referred to as “SSD(M)”) 108. The storage controller 403 is coupled tothe SSD(S) 107 and the SSD(M) 108.

Similarly to the second embodiment, the storage controller 403 includesa port 404, a processor 405, a cache memory 406, and a main memory 407.The port 404, the processor 405, the cache memory 406, and the mainmemory 407 are coupled to each other through an internal network 430.The main memory 407 stores SSD management information 270 of the SSDs,instead of the block management information 250 in the secondembodiment.

The SSD(S) 107 includes an SSD controller 101 and SLC flash memorymodules 102. The SSD controller 101 has the same configuration as theSSD controller 101 of the SSD 100 shown in FIG. 1. The SSD(M) 108includes MLC flash memory modules 103, instead of the SLC flash memorymodules 102.

The storage system 400 has at least one supplemental SSD slot 411 whichis used to add an SSD(S) 107 and an SSD(M) 108.

FIG. 12 is a diagram showing an example of SSD management information270 according to the third embodiment of the invention.

The SSD management information 270 includes an SSD conversion table 220,a substitute SSD(S) list 222, a substitute SSD(M) list 223, an SSDinformation table 224, a substitute SSD counter 226, a bad SSD counter227, a mapping table 214, and a threshold value table 230.

The SSD conversion table 220 includes a logical block address 202 and alogical block address 219 in an SSD. The logical block address 202indicates the location of a block in a logical address space. Thelogical block address 219 in an SSD indicates the address of a block ina logical address space of an SSD allocated to the logical block address202.

The storage system 400 cannot recognize the address of a physical blockof an SSD in the storage system 400, but holds a logical block addressin an SSD and associates the logical block address 202 and the logicalblock address 219 in the SSD by the SSD conversion table 220. Thelogical block address 219 in the SSD and the physical block address ofthe SSD are associated with each other in the SSD (SSD controller 101).

The substitute SSD(S) list 222 is a list of SSD(S) 107, to which nostorage area is allocated but a storage area is allocatable, from amongthe SSDs in the storage system 400. SSD number 221 is a number foruniquely identifying an SSD coupled to the storage system 400.

The substitute SSD(M) list 223 is a list of SSD(M) 108, to which nostorage area is allocated but a storage area is allocatable, from amongthe SSDs in the storage system 400.

The SSD information table 224 is a table which is used to manageinformation, such as a rewrite frequency, for each SSD in the storagesystem 400. The SSD information table 224 includes SSD number 221,SLC/MLC ID 204, rewrite frequency 208, number of substitute blocks 225,and endurance flag 210.

The SSD number 221 is a number for identifying an SSD in the storagesystem 400. The SLC/MLC ID 204 is information for identifying whetherthe type of a memory module in a corresponding SSD is SLC or MLC.

The rewrite frequency 208 is an indicator that, when a corresponding SSDbecomes a worn-out SSD, determines whether or not to set the type of asubstitute block to be allocated as a substitute to SSD(S) or SSD(M).

The number of substitute blocks 225 includes the number of substituteblocks of a memory module in a corresponding SSD. The endurance flag 210is information indicating whether or not a corresponding SSD is aworn-out SSD. An SSD with the endurance flag 210 set to “1” becomes aworn-out SSD.

The mapping table 214 is the same as that in the second embodiment.

The substitute SSD counter 226 is a counter which manages the number ofremaining substitute SSDs for each of the SSD(S) 107 and the SSD(M) 108.According to the third embodiment of the invention, substitution isperformed in an SSD unit, and thus what is necessary is that the storagesystem 400 can acquire the number of SSDs to be substitutable.

The bad SSD counter 227 is a counter which manages the SSDs to beunusable due to worn-out or physical failures.

The threshold value table 230 has the same configuration as those in thefirst embodiment and the second embodiment, but since the SSDs aremanaged by the storage controller 403, the threshold values to be setare different from those in the first and second embodiments.

When an SSD is added to the storage system 400, correspondinginformation in the SSD management information 270 is updated.Specifically, when an SSD(S) 107 is added to the storage system 400, theSSD number 221 of the added SSD(S) 107 is added to the substitute SSD(S)list 222. The quantity 212 of the substitute SSD counter 226corresponding to the SLC/MLC ID 204 is increased by the number of addedSSD(S) 107. Similarly, when an SSD(M) 108 is added to the storage system400, the SSD number 221 of the added SSD(M) 108 is added to thesubstitute SSD(M) list 222, and the quantity 212 of the substitute SSDcounter 226 corresponding to the SLC/MLC ID 204 is increased by thenumber of added SSD(M) 108.

FIG. 13 is a flowchart showing a substitution processing procedure of aworn-out SSD according to the third embodiment of the invention.

In FIG. 13, although this processing is executed when a substitute blockallocation processing is executed in the SSD, but this processing may beexecuted regularly.

The processor 405 of the storage controller 403 refers to the substituteSSD counter 226, and determines whether or not the quantity 212 of thesubstitute SSDs is equal to or larger than a prescribed threshold value(Step 350). Here, the threshold value is preferably set such that thesubstitute SSD(S) 107 and the substitute SSD(M) 108 remain. Thethreshold value needs to be set in advance, but the set threshold valuemay be changed on the basis of the status of the system.

When the quantity 212 of the substitute SSDs is smaller than theprescribed threshold value (“No” in Step 350), since a substitute SSDcannot be allocated in a short time, the processor 405 of the storagecontroller 403 displays a message to urge addition of an SSD(S) 107 oran SSD(M) 108.

The processor 405 of the storage controller 403 first determines whetheror not the number of substitute SSDs of the SSD(S) 107 is smaller than athreshold value (Step 351). When the number of substitute SSDs of theSSD(S) 107 is smaller than the threshold value (“Yes” in Step 351), amessage to urge addition of an SSD(S) 107 is displayed (Step 352).

Next, the processor 405 of the storage controller 403 determines whetheror not the number of substitute SSDs of the SSD(M) 108 is smaller than athreshold value (Step 353). When the number of substitute SSDs of theSSD(M) 108 is smaller than the threshold value (“Yes” in Step 353), amessage to urge addition of an SSD(M) 108 is displayed (Step 354).

The threshold values used in Steps 351 and 353 may be the same value ormay be set depending on the type of the memory module mounted on theSSD.

When the number of substitute SSDs is equal to or larger than thethreshold value (“Yes” in Step 350), or after a message is displayed,the processor 405 of the storage controller 403 determines whether ornot the SSD is a worn-out SSD.

The processor 405 of the storage controller 403 refers to the number ofsubstitute blocks 225 in the SSD information table 224 (Step 355), andin order to determine whether or not an SSD to be processed is aworn-out SSD, determines whether or not the number of substitute blocks225 is equal to or larger than the threshold value (Step 356). In thethird embodiment, in order to determine whether or not an SSD is wornout, the number of substitute blocks 225 which can be acquired from theSSD information table 224 is used, but for example, when informationhaving an effect on the endurance, such as an erase count, can beseparately acquired from the SSD, the acquirable information may be usedto determine whether or not an SSD is a worn-out SSD.

When the number of substitute blocks 225 is smaller than the thresholdvalue (“No” in Step 356), the processor 405 of the storage controller403 ends the SSD substitution processing.

When the number of substitute blocks 225 is equal to or larger than thethreshold value (“Yes” in Step 356), the processor 405 of the storagecontroller 403 sets the endurance flag 210 in the SSD information table224 to “1” (ON) (Step 357). Next, a processing (SSD substitutionprocessing) for allocating a substitute SSD is executed (Step 358). Thedetails of the SSD substitution processing will be described below withreference to FIG. 14.

If the substitute SSD is allocated, the processor 405 of the storagecontroller 403 deletes the SSD number 221 of the substituted SSD fromthe substitute SSD(S) list 222 or the substitute SSD(M) list 223, anddecrements the substitute SSD counter by 1 (Step 359).

The processor 405 of the storage controller 403 increments the quantity212 of the bad SSD counter 227 corresponding to the SLC/MLC ID 204 ofthe worn-out SSD by 1 (Step 360).

FIG. 14 is a flowchart showing an example of an SSD substitutionprocessing procedure according to the third embodiment of the invention.

The processor 405 of the storage controller 403 refers to the rewritefrequency 208 in the SSD information table 224 with respect to theworn-out SSD (Step 370), and determines whether or not the rewritefrequency 208 is equal to or larger than a threshold value (Step 371).

When the rewrite frequency 208 of the worn-out SSD is equal to or largerthan the threshold value (“Yes” in Step 371), since an SSD(S) 107 isallocated as a substitute SSD, the processor 405 of the storagecontroller 403 copies data stored in the worn-out SSD to the substituteSSD(S) 107 (Step 372).

The processor 405 of the storage controller 403 changes the SSD number221 corresponding to the worn-out SSD in the SSD conversion table 220 tothe SSD number 221 of the substitute SSD(S) 107 (Step 373).

When the rewrite frequency 208 of the worn-out SSD is smaller than thethreshold value (“No” in Step 371), since an SSD(M) 108 is allocated asa substitute SSD, the processor 405 of the storage controller 403 copiesdata stored in the worn-out SSD to the substitute SSD(M) 108 (Step 374).

The processor 405 of the storage controller 403 changes the SSD number221 corresponding to the worn-out SSD in the SSD conversion table 220 tothe SSD number 221 of the substitute SSD(M) 108 (Step 375).

In the above-described processing, for all the SSDs, the number ofsubstitute blocks 225 is compared with the threshold value (Step 356),but since this processing is executed when the substitute blockallocation processing is executed in the SSD, it is not necessary toexecute all the SSDs each time the processing is executed. For example,in regard to an SSD which is subjected to the substitute blockallocation processing, the above-described processing may be executedwhen the number of substitute blocks 225 becomes smaller than thethreshold value.

In the third embodiment, similarly to the second embodiment, in order toincrease reliability as the storage system, a RAID group can beconstructed. For example, if data (D) and parity (P) corresponding todata are arranged in the blocks of different SSDs, RAID4 or RAID5 may beconstructed. In this case, in regard to the type of the SSD in whichdata and parity are arranged, an SLC or an MLC may be used, or an SLCand an MLC may be used together. If the same data is stored in differentSSDs, RAID1 may be constructed. For example, RAID1 may be constructed bydifferent SSD(S) 107, SSD(M) 108, or SSD(S) 107 and SSD(M) 108 in pairs.In the third embodiment, if the RAID group is constructed, thesubstitution processing by correction copy as described with referenceto the second embodiment may be executed.

In the third embodiment, when a RAID group is constructed, as asubstitute SSD, an unused SSD may be selected, or an SSD in a differentRAID group may be selected. A preliminary SSD may be provided for eachRAID group, and the preliminary SSD may be selected as a substitute SSD.In addition, a preliminary SSD may be provided for a plurality of RAIDgroups. In this case, when an SSD has to be substituted in a RAID groupfrom among the plurality of RAID groups, the preliminary SSD may beselected as a substitute SSD.

In the third embodiment, a case in which an SSD using an SLC and an SSDusing an MLC are used together has been described, but in a case inwhich an SSD having an SLC and an MLC is used, the same substitutionprocessing may be used by adding an SSD having an SLC or an SSD havingan MLC.

Even though the storage system manages the SSDs and the flash memorypackages together, if the storage system has an addition slot for aflash memory package and an SSD addition slot, when an SSD issubstituted, the third embodiment may be applied, and when a flashmemory package is substituted, the second embodiment may be applied.

According to the third embodiment of the invention, the type of thesubstitute SSD may be selected on the basis of a parameter having aneffect on the endurance of the flash memory, such as a rewritefrequency. Specifically, if the type of a substitute SSD as a substitutefor an SSD having a high rewrite frequency is SLC, the endurance of thestorage system can be extended. In addition, if the type of a substituteSSD as a substitute for an SSD having a low rewrite frequency is MLC,bit cost can be reduced.

Fourth Embodiment

In the first to third embodiments of the invention, if a block iserased, the processing is still continuing while the block is notsubstituted until the block is worn out. In the fourth embodiment, eachtime a block is erased, a substitute block is selected and allocated.The erased block is reused as a substitute block insofar as it becomes aworn-out block.

The fourth embodiment of the invention may be applied to the first tothird embodiments. Hereinafter, an example where the fourth embodimentis applied to the SSD 100 in the first embodiment will be described withreference to FIG. 15.

FIG. 15 is a flowchart showing an example of an erase block substitutionprocessing procedure according to the fourth embodiment of theinvention.

If a write request is received, the processor 105 of the SSD controller101 determines whether or not a write data storage destination block hasto be erased (Step 381). When the storage destination block does nothave to be erased (“No” in Step 381), the erase block substitutionprocessing ends, and the writing processing is resumed.

When the write data storage destination block has to be erased (“Yes” inStep 381), the processor 105 of the SSD controller 101 executes theblock substitution processing in Step 304 of FIG. 4.

In the fourth embodiment, as described above, each time a block iserased, a storage destination is moved to a substitute block, and theerased block is reused as a substitute block. In this case, for eachsubstitute block, the erase count is recorded. Therefore, after the typeof the substitute block is selected, a substitute block having a smallerase count may be preferentially allocated. If a substitute blockhaving a small erase count is preferentially allocated, the erase countis leveled for each block, and thus the endurance of the SSD 100 can beextended. Moreover, since an erase count for a predetermined periodcannot be acquired as an indicator which is used to determine the typeof the substitute block, a time elapsed from previous erasure may beused.

The processor 105 of the SSD controller 101 deletes the physical blockaddress 203 of the substituted block from the SLC substitute block list205 or the MLC substitute block list 206 (Step 382).

The processor 105 of the SSD controller 101 refers to the blockinformation table 207, and determines whether or not the value of theerase count counter 209 of the erased block is equal to or larger than athreshold value (Step 383).

When the value of the erase count counter 209 of the erased block isequal to or larger than the threshold value (“Yes” in Step 383), theprocessor 105 of the SSD controller 101 can determine that the erasedblock is a worn-out block. Next, the processor 105 of the SSD controller101 decrements the quantity 212 of the substitute block counter by 1,and increments the quantity 212 of the bad block counter by 1 (Step384).

When the value of the erase count counter 209 of the erased block doesnot exceed the threshold value (“No” in Step 383), since the erasedblock can be reused as a substitute block, the processor 105 of the SSDcontroller 101 registers the physical address of the erased block in theSLC substitute block list 205 or the MLC substitute block list 206 (Step385).

In the block substitution processing according to the first to thirdembodiments of the invention, when a block is worn out, a block issubstituted. In the fourth embodiment, however, the block substitutionprocessing is executed each time a block is erased.

Therefore, according to the fourth embodiment of the invention, theblock substitution processing can be finely executed. As a result, theendurance of the SSD or the storage system can be extended.

1. A storage apparatus comprising: a semiconductor storage media thathas a plurality of storage devices; and a controller that is coupled tothe semiconductor storage media, wherein each of the storage devices hasan upper limit of an erase count of data stored therein, the pluralityof storage devices include a first storage device and a second storagedevice having an upper limit smaller than that of the first storagedevice, the controller includes an interface, a processor that iscoupled to the interface, and a memory that is coupled to the processor,the memory stores storage media management information that is used tomanage the semiconductor storage media, the storage media managementinformation includes area conversion information including thecorrespondence of a first address to be specified as a storagedestination of data and a second address of an area where data isstored, and a rewrite frequency of stored data is recorded for eacharea, and the controller selects an area corresponding to the firstaddress, acquires the rewrite frequency of the selected area from thestorage media management information, determines whether or not theacquired rewrite frequency is equal to or larger than a first thresholdvalue, when the acquired rewrite frequency is equal to or larger thanthe first threshold value, selects a first area to be provided by thefirst storage device, when the acquired rewrite frequency is smallerthan the first threshold value, selects a second area to be provided bythe second storage device, and sets a second address of the selectedfirst area or second area to the second address corresponding to thefirst address, to thereby update the area conversion information.
 2. Thestorage apparatus according to claim 1, wherein, when a data writerequest is received, the controller selects an area corresponding to afirst address in the data write request.
 3. The storage apparatusaccording to claim 1, wherein the controller periodically selects anarea corresponding to the first address.
 4. The storage apparatusaccording to claim 1, wherein the storage media management informationrecords the erase count of data stored in the semiconductor storagemedia for each area, and the controller acquires the erase count of theselected area from the storage media management information, and whenthe acquired erase count is equal to or larger than a second thresholdvalue, for the selected area, determines whether or not the acquirerewrite frequency is equal to or larger than the first threshold value.5. The storage apparatus according to claim 1, wherein the storage mediamanagement information is data rewritable, and includes a substitutearea list having a list of areas not corresponding to the first address,the erase count of data stored in the semiconductor storage media isrecorded for each area, and the controller selects the first area or thesecond area from the substitute area list, acquires the erase count ofthe selected area from the storage media management information, andwhen the acquired erase count is smaller than a second threshold value,adds the selected area to the substitute area list.
 6. The storageapparatus according to claim 1, wherein the rewrite frequency is thenumber of erase count of data for a predetermined period.
 7. The storageapparatus according to claim 1, wherein the rewrite frequency is set onthe basis of a time at which data stored in a corresponding area is lasterased when the corresponding rewrite frequency is acquired from thestorage media management information.
 8. The storage apparatus accordingto claim 1, wherein the storage devices are flash memory chips, thesemiconductor storage media is a flash memory module having the flashmemory chips, and the storage apparatus is a flash memory drive which iscoupled to a computer through the interface.
 9. The storage apparatusaccording to claim 1, wherein the storage devices are flash memorychips, the semiconductor storage media is a flash memory module havingthe flash memory chips, and the storage apparatus is a storage systemfrom and to which data is read and written by a host computer.
 10. Thestorage apparatus according to claim 1, wherein the storage devices areflash memory chips, the semiconductor storage media is a flash memorydrive including a flash memory module having the flash memory chips, andthe storage apparatus is a storage system from and to which data is readand written by a host computer.
 11. A method of managing a data storagearea in a storage apparatus, wherein the storage apparatus includes asemiconductor storage media that has a plurality of storage devices, anda controller that is coupled to the semiconductor storage media, each ofthe storage devices has an upper limit of an erase count of data storedtherein, the plurality of storage devices include a first storage deviceand a second storage device having an upper limit smaller than that ofthe first storage device, the controller includes an interface, aprocessor that is coupled to the interface, and a memory that is coupledto the processor, the memory stores storage media management informationthat is used to manage the semiconductor storage media, the storagemedia management information includes area conversion informationincluding the correspondence of a first address to be specified as astorage destination of data and a second address of an area where datais stored, and a rewrite frequency of stored data is recorded for eacharea, and the method comprising: causing the controller to select anarea corresponding to the first address; causing the controller toacquire the rewrite frequency of the selected area from the storagemedia management information; causing the controller to determinewhether the acquired rewrite frequency is equal to or larger than afirst threshold value; when the acquired rewrite frequency is equal toor larger than the first threshold value, causing the controller toselect a first area to be provided by the first storage device; when theacquired rewrite frequency is smaller than the first threshold value,causing the controller to select a second area to be provided by thesecond storage device; and causing the controller to set a secondaddress of the selected first area or second area to the second addresscorresponding to the first address, to thereby update the areaconversion information.
 12. The method according to claim 11, furthercomprising: when a data write request is received, causing thecontroller to select an area corresponding to a first address in thedata write request.
 13. The method according to claim 11, wherein thestorage media management information records the erase count of datastored in the semiconductor storage media for each area, and the methodfurther comprising: causing the controller to acquire the erase count ofthe selected area from the storage media management information; andwhen the acquired erase count is equal to or larger than a secondthreshold value, causing the controller to, for the selected area,determine whether or not the acquired rewrite frequency is equal to orlarger than the first threshold value.
 14. The method according to claim11, wherein the storage media management information is data rewritable,and includes a substitute area list having a list of areas notcorresponding to the first address, the erase count of data stored inthe semiconductor storage media is recorded for each area, and themethod further comprising: causing the controller to select the firstarea or the second area from the substitute area list; causing thecontroller to acquire the erase count of the selected area from thestorage media management information; and when the acquired erase countis smaller than a second threshold value, causing the controller to addthe selected area to the substitute area list.
 15. A storage apparatuscomprising: a flash memory module that has a plurality of flash memorychips; and a controller that is coupled to the flash memory module,wherein each of the flash memory chips has an upper limit of an erasecount of data stored therein, the plurality of flash memory chipsinclude a first flash memory chip and a second flash memory chip havingan upper limit smaller than that of the first flash memory chip, theflash memory chips are managed in a block unit of a predetermined size,the controller includes an interface, a processor that is coupled to theinterface, and a memory that is coupled to the processor, the memorystores block management information which is use to manage the blocks,the block management information includes block conversion informationincluding correspondence of a logical address to be specified as a datastorage destination and a physical address which is a physical addressof a block, in which data is stored, and a substitute block list whichis data rewritable and has a list of blocks not corresponding to thelogical address, a rewrite frequency which is an erase count of data ineach block for a predetermined period, and an erase count of data storedin the corresponding block are recorded, and when a data write requestwith respect to the flash memory module is received, the controllerspecifies the physical address corresponding to the logical address inthe data write request on the basis of the block conversion information,to thereby specify a block in which requested data is written, acquiresa rewrite frequency of the specified block from the storage mediamanagement information, determines whether or not the acquired rewritefrequency is equal to or larger than a first threshold value, when theacquired rewrite frequency is equal to or larger than the firstthreshold value, selects a first block in the first flash memory chipfrom the substitute block list and writes requested data in the selectedfirst block, when the acquired rewrite frequency is smaller than thefirst threshold value, selects a second block in the second flash memorychip from the substitute block list and writes requested data in theselected second block, and after requested data is written, sets thephysical address of the block, in which requested data is written, tothe physical address corresponding to the logical address in the datawrite request, to thereby update the block conversion information.